AF1 with New (N) Recurring (R) Unfinished (U)
Original Post
I prefer the flow of AF1 compared with AF4 Revised.
Is there value in using AF1 and coding items as (N) (R) (U)?
Proposed benefits: 1. AF1 seems like a more elegant sytem compared with AF4R.
2. It's still possible to audit / snap shot the number of each item type.
3. It's still possible to dismiss items at the New stage before getting into a commitment and / or taking on too many things at once.
By the way, my use of 'New' would basically be for those items at a 'project level' and above that have not been initiated at all.
Has anyone already tried this?
Is there value in using AF1 and coding items as (N) (R) (U)?
Proposed benefits: 1. AF1 seems like a more elegant sytem compared with AF4R.
2. It's still possible to audit / snap shot the number of each item type.
3. It's still possible to dismiss items at the New stage before getting into a commitment and / or taking on too many things at once.
By the way, my use of 'New' would basically be for those items at a 'project level' and above that have not been initiated at all.
Has anyone already tried this?
Reply by Mark Forster
leon:
I love AF1 myself, and prefer the "feel" of it to any other system. I am however aware that it has some deficiencies. Unfortunately all my attempts to improve AF1 have to a greater or lesser extent destroyed the "feel".
I love AF1 myself, and prefer the "feel" of it to any other system. I am however aware that it has some deficiencies. Unfortunately all my attempts to improve AF1 have to a greater or lesser extent destroyed the "feel".
Reply by Cricket
For sporadic use, AF1 works better than AF4. The fixed size of the closed list (one page) is more consistent. It also works better with "Finally! I can tear out this page.")
Until I wrote the next bit, and realized I couldn't balance the pros/cons columns, I thought AF1 with NRU pages would work well. Now I think the "different" is actually breaking one AF1's key benefits.
I do Recurring tasks fairly quickly. I've already evaluated them many times before. Unfinished take a bit longer, since many are long-term, low-commitment projects that get dropped when the week gets busy, but I have invested enough time that I don't want to dismiss them. New take even longer and are the ones most at risk of dismissal.
Under AF1, there are a few long-lived New tasks on each page. Under AF1 with N/R/U they'd all be on one page.
Under the original AF1, as a page nears dismissal we have only a few tasks to choose from if we want to keep it open. That can lead to admitting we won't do any of them (good) or finally doing the tough one (good), or picking an unimportant one just so we can keep the page open without doing the tough one (bad).
With AF1-NRU, there's a much longer list to choose from. It can take many passes before we have to deal with the tough one (bad).
The organized part of me wants to separate Recurring from New and Unfinished. Recurring often have a short cycle so are written often. It feels like they waste space on the page. They're usually more important, so I want them visible.
The part that gets things done likes the effect of a few remaining things on the page.
Until I wrote the next bit, and realized I couldn't balance the pros/cons columns, I thought AF1 with NRU pages would work well. Now I think the "different" is actually breaking one AF1's key benefits.
I do Recurring tasks fairly quickly. I've already evaluated them many times before. Unfinished take a bit longer, since many are long-term, low-commitment projects that get dropped when the week gets busy, but I have invested enough time that I don't want to dismiss them. New take even longer and are the ones most at risk of dismissal.
Under AF1, there are a few long-lived New tasks on each page. Under AF1 with N/R/U they'd all be on one page.
Under the original AF1, as a page nears dismissal we have only a few tasks to choose from if we want to keep it open. That can lead to admitting we won't do any of them (good) or finally doing the tough one (good), or picking an unimportant one just so we can keep the page open without doing the tough one (bad).
With AF1-NRU, there's a much longer list to choose from. It can take many passes before we have to deal with the tough one (bad).
The organized part of me wants to separate Recurring from New and Unfinished. Recurring often have a short cycle so are written often. It feels like they waste space on the page. They're usually more important, so I want them visible.
The part that gets things done likes the effect of a few remaining things on the page.
Reply by Alan Baljeu
It seems to me you could mark each page new, recurring, or unfinished just as in AF4r, then follow the Af1 flow through those pages. But I have serious doubts whether the recurring pages could cope with Af1 dismissal rules so maybe something different there or drop the category.
Mark: so you're less satisfied with SAF? Is it just "less fun" or is there something more specific you don't like about it?
Mark: so you're less satisfied with SAF? Is it just "less fun" or is there something more specific you don't like about it?
Reply by Rainer
Leon,
several days ago I did what you wrote in your above post and the result was abhorring.
The problem is: that what Mark calls the "feel" is our own perception of our own instinctive reaction towards a certain item on the AF1 list. This perception gets blured or disturbed by attaching a logical tag or code to the item. Thus the list "feels dead" when this code is added.
The question is: What kind of decisions need to have that instinctive "gut feeling" input, and which decisions must be based on our logical mind? And why do we have trouble doing both at the same time?
several days ago I did what you wrote in your above post and the result was abhorring.
The problem is: that what Mark calls the "feel" is our own perception of our own instinctive reaction towards a certain item on the AF1 list. This perception gets blured or disturbed by attaching a logical tag or code to the item. Thus the list "feels dead" when this code is added.
The question is: What kind of decisions need to have that instinctive "gut feeling" input, and which decisions must be based on our logical mind? And why do we have trouble doing both at the same time?
Reply by Seraphim
Mark wrote:
<<>>
And Alan Baljeu wrote:
<<>>
I have the same question, Mark. You wrote that SAF is "streets ahead of any of my other systems" (http://www.markforster.net/forum/post/1303467#post1303472). But then you dropped it pretty quickly when you came up with the AF4 Revised approach.
Personally I find SAF preserves much, if not all, of the feel of AF1, but the 2nd column idea gives you a great deal more control. It solves AF1's inability to deal with "urgent".
My experiment combining SAF with the Recurring, Unfinished, and New pages of AF4R is going very well. (http://www.markforster.net/forum/post/1330080)
I'm getting lots done, and feel more in control than with any other system I've tried, including DWM. And it still feels very much like AF1 -- almost meditative. I can't believe how fast the days have been going by.
I do miss the workload-gauging feature that DWM provided. SAF doesn't provide nearly as clear a picture. But the other benefits outweigh this.
<<>>
And Alan Baljeu wrote:
<<
I have the same question, Mark. You wrote that SAF is "streets ahead of any of my other systems" (http://www.markforster.net/forum/post/1303467#post1303472). But then you dropped it pretty quickly when you came up with the AF4 Revised approach.
Personally I find SAF preserves much, if not all, of the feel of AF1, but the 2nd column idea gives you a great deal more control. It solves AF1's inability to deal with "urgent".
My experiment combining SAF with the Recurring, Unfinished, and New pages of AF4R is going very well. (http://www.markforster.net/forum/post/1330080)
I'm getting lots done, and feel more in control than with any other system I've tried, including DWM. And it still feels very much like AF1 -- almost meditative. I can't believe how fast the days have been going by.
I do miss the workload-gauging feature that DWM provided. SAF doesn't provide nearly as clear a picture. But the other benefits outweigh this.
Reply by Mark Forster
Seraphim:
The trouble with me is that when I think of an idea I've got to try it out. Unfortunately it's not possible to try out more than one system at a time.
I am of course already working on something completely different.
The only people who can afford to chop and change systems like this are those who invent time management systems for a living or those who are retired. Fortunately I have ticked both boxes!
The trouble with me is that when I think of an idea I've got to try it out. Unfortunately it's not possible to try out more than one system at a time.
I am of course already working on something completely different.
The only people who can afford to chop and change systems like this are those who invent time management systems for a living or those who are retired. Fortunately I have ticked both boxes!
Reply by Alan Baljeu
So Seraphim's approach is here:
http://www.markforster.net/forum/post/1330080
I've taken a rather different approach. I've been gradually grouping things by "project" (i.e. anything that has more than one task, such as designing a rocket, cleaning my house, people to do stuff with, working out at the gym). When I find a task fits in a "project", I may move it in. But I also leave many tasks loose. In this approach:
- Recurring tasks are in with a project, not in a Recurring list.
- Unfinished tasks are in Active projects.
- New stuff is generally on a New page.
- There is no Old (that's an AF4 concept).
- When I finish current tasks in a project, I send the project to an Inactive Projects section.
I run SAF over New and Active pages together, and my own system to reactivate inactive tasks.
http://www.markforster.net/forum/post/1330080
I've taken a rather different approach. I've been gradually grouping things by "project" (i.e. anything that has more than one task, such as designing a rocket, cleaning my house, people to do stuff with, working out at the gym). When I find a task fits in a "project", I may move it in. But I also leave many tasks loose. In this approach:
- Recurring tasks are in with a project, not in a Recurring list.
- Unfinished tasks are in Active projects.
- New stuff is generally on a New page.
- There is no Old (that's an AF4 concept).
- When I finish current tasks in a project, I send the project to an Inactive Projects section.
I run SAF over New and Active pages together, and my own system to reactivate inactive tasks.
Reply by FocusGuy.
@Alan
I tried this approach and really it was a disaster for me.
So I gona talk about projects.
finally I found another way for my MIP (most important project). I realised I could take a binder and put in it my most important handwriting projects.
The way I manage these project is simple. There are none details but only my big rocks. I can draw them in a square, a euristic scheme, 5 or 6 word or sometime or make a simple sentence.
For the moment I have only a few project pages. (now 4)
On another hand, Many project need an historical reporting. I just opened a word sheet (oup sorry a page sheet (i am on mac) or a text edit page, put it apart in my Mac's folder and do my historical reporting like this :
2010-11-09 I sent this to client X
2010-11-10 I did this and that
So,
I keep AF4R for working on the active and actionable tasks
And added a page where there is a handwriting UNFINISHED project page
I noticed that I just put the bigs Rock of it such as
Project X / DO THIS/ DO THAT/ THEN THAT/ THEN THIS/ AND END WITH THAT
When something is new eg Project X DO THAT it goes on my NEW PAGE with the others tasks until I do it and of course DO THIS on my unfinished project page is crossed.
With this method i realized i could follow many projects very easily and have my project page in its binder apart, only for what is absolutely necessary.
But I admit that if your project tasking works for you it's great for you.
I tried this approach and really it was a disaster for me.
So I gona talk about projects.
finally I found another way for my MIP (most important project). I realised I could take a binder and put in it my most important handwriting projects.
The way I manage these project is simple. There are none details but only my big rocks. I can draw them in a square, a euristic scheme, 5 or 6 word or sometime or make a simple sentence.
For the moment I have only a few project pages. (now 4)
On another hand, Many project need an historical reporting. I just opened a word sheet (oup sorry a page sheet (i am on mac) or a text edit page, put it apart in my Mac's folder and do my historical reporting like this :
2010-11-09 I sent this to client X
2010-11-10 I did this and that
So,
I keep AF4R for working on the active and actionable tasks
And added a page where there is a handwriting UNFINISHED project page
I noticed that I just put the bigs Rock of it such as
Project X / DO THIS/ DO THAT/ THEN THAT/ THEN THIS/ AND END WITH THAT
When something is new eg Project X DO THAT it goes on my NEW PAGE with the others tasks until I do it and of course DO THIS on my unfinished project page is crossed.
With this method i realized i could follow many projects very easily and have my project page in its binder apart, only for what is absolutely necessary.
But I admit that if your project tasking works for you it's great for you.
Reply by Alan Baljeu
Thanks for sharing , Jupiter. To be honest I am not yet sure it's working great for me either :-)
But it's definitely fun and certainly not a disaster although I can easily see how it may be so. It's my system so I know how I use it and how I want it to behave and I'm constantly mindful of ways it can misbehave.
That said, what you have for projects looks great, likely even better than my approach, but for me now, would not be as fun :-)
(PS. It's not all about fun and games. I'm also getting important work done too.)
But it's definitely fun and certainly not a disaster although I can easily see how it may be so. It's my system so I know how I use it and how I want it to behave and I'm constantly mindful of ways it can misbehave.
That said, what you have for projects looks great, likely even better than my approach, but for me now, would not be as fun :-)
(PS. It's not all about fun and games. I'm also getting important work done too.)
Reply by Alan Baljeu
I wrote:
<>
It turns out that moving projects is tedious in paper (though not in OneNote) and finding projects later is a chore when they are scattered. So I resolved instead to have a list of unfinished tasks, a list of projects with no current tasks, and to divide this list ala Af4. Logically everything is still the same, but physically it's different.
So now my pages are New Tasks, Unfinished Tasks, Recent Projects, Old Projects.
Some "projects" Consist of recurring items.
<
It turns out that moving projects is tedious in paper (though not in OneNote) and finding projects later is a chore when they are scattered. So I resolved instead to have a list of unfinished tasks, a list of projects with no current tasks, and to divide this list ala Af4. Logically everything is still the same, but physically it's different.
So now my pages are New Tasks, Unfinished Tasks, Recent Projects, Old Projects.
Some "projects" Consist of recurring items.